System and method for managing wireless point-of-sale transactions

ABSTRACT

A system that enables a wireless point-of-sale transaction. In one embodiment the system comprises an account module, an account selection module, a display, an input interface, and a wireless transmitter. The account module stores account information corresponding to a plurality of payment accounts. The account selection module selects a payment account from the plurality of payment accounts as a default payment account for a wireless point-of-sale transaction based on one or more predetermined criteria. The display displays the default payment account to a user. The input interface enables the user to accept the default payment account by the account selection module. The wireless transmitter that wirelessly transmits payment information to a point-of-sale device, wherein the payment information comprises account information associated with the default account when the default payment account is accepted via the input interface.

FIELD OF THE INVENTION

The invention relates to the enablement and management of wirelesspoint-of-sale payments by a user physically present at brick-and-mortarretailers.

BACKGROUND OF THE INVENTION

The use of wireless technologies, such as “smart card” technology tomake wireless payments at brick-and-mortar retail locations is generallyknown. However, typically payment cards that use these technologies areonly a wireless substitute for cards implementing older accountidentification methods, such as magnetic strips, or carbon copying.Conventional smart cards are passive components that do not enableactive management of multiple accounts by a user. These and otherdrawbacks associated with known wireless point-of-sale payment systemsare known.

SUMMARY

One aspect of the invention relates to a system that enables a wirelesspoint-of-sale transaction. In one embodiment the system comprises anaccount module, an account selection module, a display, an inputinterface, and a wireless transmitter. The account module stores accountinformation corresponding to a plurality of payment accounts. Theaccount selection module selects a payment account from the plurality ofpayment accounts as a default payment account for a wirelesspoint-of-sale transaction based on one or more predetermined criteria.The display displays the default payment account to a user. The inputinterface enables the user to accept the default payment account by theaccount selection module. The wireless transmitter that wirelesslytransmits payment information to a point-of-sale device, wherein thepayment information comprises account information associated with thedefault account when the default payment account is accepted via theinput interface.

Another aspect of the invention relates to a system that enables awireless point-of-sale transaction. In one embodiment the systemcomprises an account module, a display, an input interface, and awireless transmitter. The account module stores account informationcorresponding to a plurality of payment accounts. The display displaystwo or more of the payment accounts stored by the account module to auser. The input interface enables the user to select one of the paymentaccounts displayed by the display. The wireless transmitter wirelesslytransmits payment information to a point-of-sale device, wherein thepayment information comprises account information associated with theselected payment account.

Another aspect of the invention comprises a system that enables awireless point-of-sale transaction. In one embodiment, the systemcomprises an account module, an input interface, a transmitter, and areceiver. The account module stores account information corresponding toa payment account, wherein the account information comprises balanceinformation related to the payment account. The input interface enablesa user to initiate wireless point-of-sale transactions. The transmitterwirelessly transmits payment information to a point-of-sale device inresponse to the initiation of the wireless point-of-sale transactions,wherein the payment information comprises account information associatedwith the payment account stored by the account module. The receiverreceives a wireless transmission of purchase information, wherein thepurchase information comprises price information related to the wirelesspoint-of-sale transaction. Further, the balance information stored bythe account module is updated based on the price information related tothe wireless point-of-sale transactions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system that enables the execution and management ofwireless point-of-sale transactions, according to one or moreembodiments of the invention.

FIG. 2 illustrates a system that enables the execution and management ofwireless point-of-sale transactions, according to one or moreembodiments of the invention.

FIG. 3 illustrates a system that enables the execution and management ofwireless point-of-sale transactions, according to one or moreembodiments of the invention.

FIG. 4 illustrates a system that enables the execution and management ofwireless point-of-sale transactions, according to one or moreembodiments of the invention.

FIG. 5 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 6 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 7 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 8 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 9 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 10 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 11 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 12 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 13 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 14 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 15 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 16 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 17 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 18 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 19 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 20 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 21 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 22 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 23 illustrates a user interface, in accordance with one or moreembodiments of the invention.

FIG. 24 illustrates a user interface, in accordance with one or moreembodiments of the invention.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 10 that enables the execution and managementof wireless point-of-sale transactions, according to one or moreembodiments of the invention. System 10 may include a wireless clientdevice 12, a point-of-sale device 14, and one or more financialinstitutions 16. System 10 may enable a user to execute a point-of-saletransaction by initiating a wireless transmission of transactioninformation from wireless client device 12 to point-of-sale device 14.

In one implementation of the invention, wireless client device 12 mayinclude a “handheld” electronic client device capable of storing andmanaging account information associated with one or more paymentaccounts, and wirelessly transmitting and/or receiving information. Forexample, wireless client device 12 may comprise a Personal DigitalAssistant, a handheld computer, a radio telephone, a satellitetelephone, a pager, a personal music player, or other client devices.

In one implementation of the invention, point-of-sale device 14 mayinclude a point-of-sale device located at a brick-and-mortar retailer,and may enable individuals to purchase goods and/or services from theretailer. For instance, point-of-sale device 14 may comprise a cashierstation within a retail store (e.g., a supermarket checkout, adepartment store register, an electronics store register, etc.), anautomated point-of-sale station associated with the retailer (e.g., agasoline station “pay at the pump” device, an automated supermarketcheckout, etc.), or other point-of-sale devices.

Financial institutions 16 may include one or more institutions withwhich the user maintains payment accounts. For example, financialinstitutions 16 may comprise a lender, a bank, a credit card company, aretailer (e.g., a retailer that extends lines of credit to customers), afinancing company, and/or other financial institutions. A paymentaccount may include any account from which a retailer may receivepayment (or make payment to) based on the user's interaction with apoint-of-sale device (e.g., point-of-sale device 14). Some non-limitingexamples of a payment account may include a checking account, a savingsaccount, a money market account, a pre-paid account, a credit account, acredit card account, and/or other payment accounts.

According to one implementation of the invention, the user may initiatea point-of-sale transaction by specifying one or more goods and/orservices for purchase from the retailer associated with point-of-saledevice 14. The goods and/or services specified by the user may beconveyed to point-of-sale device 14 (e.g. during “check out”), and atotal cost to the user for the transaction may be determined bypoint-of-sale device 14. Wireless client device 12 may enable the userto select a payment account from which funds are transferred as part ofa wireless point-of-sale transaction, and may enable payment informationto be transmitted wirelessly to point-of-sale device 14 as part of theexecution of the wireless transaction. The payment information maycomprise account information associated with the selected paymentaccount. For instance, the payment information may be wirelesslytransmitted from wireless client device 12 to point-of-sale device 14.The wireless transmission of payment information from wireless clientdevice 12 to point-of-sale device 14 may comprise a transmission viavirtually any wireless medium and/or protocol presently know oravailable in the future. For instance, the wireless medium and/orprotocol may comprise Bluetooth, Bluetooth 2.1, infrared transmission,radio frequency transmission (e.g., direct transmission or transmissionvia a base station), and/or other wireless media and/or protocols.

Upon receipt of the payment information, point-of-sale device 14 maygenerate a request for payment from a financial institution associatedwith the payment account selected by the user on wireless client device12. In one implementation, the payment request may be transmitted to thefinancial institution, which may respond with a payment response thatmay be transmitted back to point-of-sale device 14. The payment responsemay comprise a promise to make the payment and/or a paymentconfirmation.

After receiving the payment response, point-of-sale device 14 maygenerate a transaction record to be provided to the user along with thegoods and/or service purchased. In some instances, a transaction recordmay also be provided to the financial institution that transmitted thepayment response. One or both of the transaction record provided to theuser and/or the financial institution may include a paper record of thetransaction, an electronic record of the transaction, or both. It shouldbe appreciated that the forms of the two transaction records need not bethe same. For example, in one implementation, the user may be providedwith a paper record and the financial institution may be provided withan electronic record, or vice versa. Further, the information and levelof detail of the two transaction records may also be different. In theinstances in which the transaction record provided to the user comprisesan electronic record of the transaction, the electronic record may betransmitted wirelessly from point-of-sale device 14 to wireless clientdevice 12. The electronic record received by wireless client device 12may then be processed and/or stored for future access by the user. Forinstance, the electronic record may be stored locally on wireless clientdevice 12, and/or wireless client device 12 may wirelessly transmit theelectronic record to an alternate client 18 for remote storage. In onenon-limiting example, the electronic record may be temporarily stored onwireless client device 12 and transmitted at a later time (selectedautomatically or by the user) to alternate client 18 for more permanentstorage. Communication of electronic records, and/or other information,between wireless client device 12 and alternate client 18 may comprisewireless communications implementing any of the electronic media and/orprotocols previously mentioned and/or wired communication (e.g., via adocking station or networking port).

Alternate client 18 may comprise an electronic processing device withmore processing power and/or storage capacity than wireless clientdevice 12. For example, alternate client device 12 may include a desktopcomputer, a laptop computer, and/or other client devices.

It should be appreciated that various ones of the depicted operativelinks between wireless client device 12, point-of-sale device 14,financial institutions 16, and alternate client 18 may not be present insome of the embodiments of the invention, or an operative link shown inFIG. 1 as being enabled for transmitting information in either directionmay be implemented in some embodiments as a one-way link. For example,in one embodiment, wireless client device 12 may not receive informationfrom some or all of financial institutions 16 without the informationfirst being relayed to alternate client 18. As another example, in oneembodiment, alternate client 18 may not be implemented at all. As yetanother example, in one embodiment, information is wirelesslytransmitted from wireless client device 12 to point-of-sale device 14,but information may not be transmitted from point-of-sale device 14 towireless client device 12. Other examples also exist.

FIG. 2 illustrates system 10 according to one or more embodiments of theinvention. As shown in FIG. 2, system 10 may include one or moreprocessors 20, a user interface 22, a data storage 24, a wirelesstransmitter/receiver 26 (e.g., a single component that both transmitsand receives, separate components for transmitting and receiving, etc.),and/or other components.

As can be seen in FIG. 2, user interface 22 may comprise an inputinterface 28 and a display 30. Input interface 28 may comprise one ormore devices that enable the user to input information and/or commandsto processor 20. For instance, input interface 28 may comprise akeyboard, a keypad, a mouse, a joystick, a button, a knob, a solid-stateinput device, a lever, a touchpad, a touchscreen, a switch, a trackball,and/or other input devices. Display 30 may visually convey informationto the user. For example, display 30 may include a pixilated electronicdisplay such as an LCD display, an OLED display, a micro-mirror devicedisplay, other pixilated electronic displays, and/or other displays. Insome implementations, user interface 22 may comprise other sensoryfeedback mechanisms to convey information to the user. As a non-limitingexample, user interface 22 may comprise an audible feedback system(e.g., a speaker system, etc.), a sensory feedback system, and/or othersensory feedback systems. In one or more implementations, user interface22 may comprise at least one input interface and at least one displayprovided on wireless client device 12.

Data storage 24 may comprise one or more electronic storage media thatenable storage of information (e.g., payment account information,transaction information, user-spending information, etc.). The storagemedia of data storage 24 may comprise any electronic storage mediumcurrently known or available in the future. In some instances, datastorage 24 may comprise a single storage medium within a single storagedevice. In other instances, data storage 24 may comprise one or morestorage media within a plurality of separate devices which may or maynot be in communication with each other.

Transmitter/receiver 26 may comprise one or more components capable oftransmitting and receiving wireless information over a wirelesscommunications link. In some implementations, transmitter/receiver 26may include a plurality of transmitters and/or receivers that enablewireless communication via a plurality of different wirelesscommunication media and/or protocols. Further, transmitter/receiver may,in practice, include separate transmitters and/or receivers associatedwith a plurality of devices to enable wireless communication ofinformation to and from processor 20, user interface 22, and/or datastorage 24. In some instances, transmitter/receiver 26 may comprise morethan one transmitter and/or more than one receiver associated with asingle device. This may enable the single device communicate wirelesslyvia more than one wireless medium and/or protocol.

In one or more implementations of the invention, processor 20 mayexecute one or more modules comprising an account module 32, an accountselection module 34, a user-spending module 36, alert module 38 and/orother modules. Modules 32, 34, 36, and 38 may be implemented as hardwaremodules, software modules, firmware modules, or as a combination ofhardware, software and/or firmware. Modules 32, 34, 36, and 38 may beexecuted locally to each other (e.g., on the same device), or remotelyfrom each other (e.g., in separate devices interfacing via an operativelink). In some embodiments of the invention, the functionality of asingle module may be provided within a plurality of sub-modules (notshown) being executed remotely from each other. In one or moreembodiments of the invention, processor 20 may comprise a singleprocessor. In some instances, the single processor may be disposedwithin a single device (e.g., wireless client device). However, suchinstances are not limiting, and in other instances processor 20 maycomprise a plurality of processors that may be located within a singledevice or within separate devices. In most implementations, processor 20comprises at least one processing component within wireless clientdevice 12.

Account module 32 may store account information associated with aplurality of payment accounts that the user has access to. Accountmodule 32 may store the account information in data storage 24, and maymanage the information, information structure, and/or other aspects ofthe storage of the account information. Some non-limiting examples ofaccount information may include an account number, a routing number, acard number, an institution associated with an account (e.g., a bank,etc.), an account balance, one or more transaction records, accountholder information (e.g., name, social security number, birthday,address, etc.) associated with a holder of a payment account (e.g., theuser and/or other holders), security information associated with apayment account (e.g., a password, a personal identification number,biometric information, etc.), and/or other account information. Thestored account information may be updated manually and/or automatically.For example, when one of the payment accounts is used to make a payment(or receive a credit) in a wireless point-of-sale transaction, balanceinformation associated with the payment account may be updated toreflect the funds transferred in the wireless point-of-sale transaction.

When a wireless transaction is initiated, account selection module 34selects a payment account as a default payment account for a wirelesspoint-of-sale transaction based on one or more predetermined criteria.The default payment account may be selected by account selection module34 from the payment accounts associated with the account informationstored by account module 32. As is discussed further below, the one ormore predetermined criteria may comprise one or more criteria based on aretailer, a physical location, an account balance, a type (e.g., aclassification) of a good and/or service being purchased, a transactionamount, a time, a user preference, user spending information thatincludes one or more aspects of one or more transaction records of oneor more previous wireless point-of-sale transactions, and/or othercriteria based on other considerations.

In some instances, display 30 may convey the selection of the defaultaccount to the user. Input interface 28 may then enable the user toaccept or reject the default payment account selected by accountselection module 34. If the user accepts the default payment account,payment information including account information associated with thedefault payment account may be transmitted wirelessly from wirelessclient device 12 to facilitate the wireless point-of-sale transaction.In one or more implementations, the selection of the default account byaccount selection module 34 may include ranking a plurality paymentaccounts from most likely to be used by the user for that particulartransaction to least likely to be used by the user for that particulartransaction based on the one or more predetermined criteria. In oneimplementation, display 30 may display to the user more payment accountsthan the payment account ranked most likely to be used. For example,display 30 may display the 5 payment accounts most likely to be used (ina manner representative of their order and/or relative likelihood ofusage). In such implementations, as well as in implementations in whichonly the payment account ranked most likely to be use is displayed,input interface 28 enables the user to reject the default paymentaccount selected by account selection module 34 and manually select auser-preferred payment account from the plurality of accounts stored inaccount module 32. Additional functionality may also be provided byaccount spending module 34.

User spending module 36 may track the user's spending based ontransaction information received via transmitter/receiver 26. Forexample, the transaction information may include transaction records,transaction amounts, and/or other transaction information. User spendingmodule 36 may track user spending with respect to a total amount spentover a specified (automatically and/or manually) time period, spendingat a specified (automatically and/or manually) retailer or group ofretailers, spending at a specified (automatically and/or manually)location or group of locations, spending using a specified(automatically and/or manually) account or group of accounts, spendingon a specified (automatically and/or manually) type of good and/orservice or group of types of goods and/or services, current balance(s)on one or more specified (automatically and/or manually) accounts, otherconsiderations, and/or a combination of considerations.

In some implementations, input interface 28 enables the user to inputone or more spending thresholds that are stored by user spending module36. User spending module 36 may store the spending thresholds in datastorage 24. A spending threshold may include a monetary amount, one ormore transaction criteria (e.g., one or more payment accounts, one ormore classifications of goods and/or services, one or more retailers,one or more locations, etc.), a payment account criteria (e.g., abalance, etc.), and/or a time period (e.g., a specified interval from aspecified start time, a series of periodic intervals, a specifiedinterval from a “trigger”, etc.). As an example, a spending thresholdmay be input by the user that includes a threshold monetary amount, aspecified type of good and/or service, and a threshold time period. Ifthe user exceeds the threshold monetary amount during the threshold timeperiod, on goods and/or services of the specified type, the spendingthreshold has been breached. As another example, a spending thresholdmay be input by the user including a threshold monetary amount and aspecified payment account. If the user exceeds the threshold monetaryamount in a single transaction on the specified account, the spendingthreshold has been breached. It should be appreciated that theseexamples are not limiting, and that an array of possible spendingthresholds is possible based on the types of information presented abovethat may be used to establish a spending threshold.

User spending module 36 may compare the user's spending with thespending thresholds established by the user. When a spending thresholdis breached, a predetermined action may be executed by processor 20. Forexample, alert module 38 may generate an alert. The alert generated byalert module 38 may be provided to the user and/or to a third party. Analert may include a visual alert, an audible alert, and/or another typeof alert provided on wireless client device 12. Alerts provided to theuser may enable the user to track her spending. For instance, the usermay set one or more spending thresholds based on a budget, and thealerts may apprise the user of her compliance with, or spending withrespect to, the budget. In some implementations, alerts may be scheduledby the user to be triggered by user spending at levels that are lessthan the ultimate budget. Such implementations may provide the user withwarnings and/or reminders that may enhance the ability of the user toadhere to a predetermined budget.

Alerts provided to third parties may enable the third parties to beinformed of the user's spending habits. For example, a third partydesiring to receive third party alerts in order to follow the user'sspending may include a spouse, a parent, an administrator, a boss, apartner, a joint account holder, and/or other third parties. Third partyalerts may be provided to the third party via virtually any form ofcommunication. For instance, third party alerts may be sent as emails,text-messages (e.g., SMS messages, etc.), automated phone calls,traditional postal mail, and/or other forms of communication.

It should be appreciated that the depictions of information transmittedbetween entities such as wireless client device 12, processor 20, userinterface 22, data storage 24, transmitter/receiver 26, point-of-saledevice 14, financial institutions 16, and/or alternate client 18 inFIGS. 1 and 2 are exemplary only, and that the scope of the inventionincludes implementations comprising other information paths that enablesystem 10 to provide some or all of the described functionality withrespect to wireless point-of-sale transactions in which the user isphysically present at a brick-and-mortar point-of-sale device, andenables a payment to a retailer associated with the point-of-sale deviceby wireless client device 12.

For instance, some implementations may include interaction with atransaction server that manages communications between some or all ofwireless client device 12, point-of-sale device 14, financialinstitutions 16, and/or alternate client device 18. In someimplementations, the transaction server may be associated with one ormore organizations and/or institutions that facilitate wirelesspoint-of-sale transactions. For example, one or more of financialinstitutions 16 may provide and/or maintain the transaction server. Asanother example, the transaction server may be provided and/ormaintained by a third-party that would not otherwise be involved in thetransaction.

FIG. 3 illustrates an implementation of system 10 including atransaction server 40. As is shown, transaction server 40 may act as a“firewall” between financial institutions 16 and wireless client device12 and alternate client 18. Although depicted as a single server,transaction server 40 may comprise a plurality of servers, some or allof which may be in communication with each other. In some instances, asingle transaction server 40 (or a group of transaction servers incommunication with each other) may provide a firewall for a plurality offinancial institutions. In other instances, each financial institutionmay have its own dedicated transaction server 40.

In addition to acting as a firewall, transaction server 40 may providesome of the functionality of processor 20 described above. For example,transaction server 40 may maintain information associated with usersthat may be accessed remotely by wireless client device 12 and/oralternate client 18. In one such instance, account information, userspending information, spending thresholds, transaction records, userinformation, and/or other information associated with a user may bestored and/or managed by server 40. In some implementations, third partyalerts may be transmitted to third parties from transaction server 40.

In one or more implementations of the invention, transaction server 40may provide a firewall through which point-of-sale device 14communicates with financial institutions 16, as well as wireless clientdevice 12 and alternate client 18. One such implementation isillustrated in FIG. 4. Other implementations utilizing these and/orother information paths and/or other entities are contemplated withinthe scope of the invention.

FIG. 5 illustrates user interface 22, according to one or moreimplementations of the invention. User interface 22 may convey one ormore action options 42 to the user. Action options 42 may enable theuser to select an action for execution by system 10. Action options 42may comprise an initiate transaction option, a view spending historyoption, a set defaults option, a set thresholds option, an informationsynchronization option, a search transaction records option, and/orother action options.

Selection of an initiate transaction option may initiate a wirelesspoint-of-sale transaction. Other events may also initiate a wirelesspoint-of-sale transaction, such as receiving a transaction request frompoint-of-sale device 14, or other events. Once a wireless point-of-saletransaction is initiated, user interface 22 may present the user with adefault payment account. As was discussed above, the default paymentaccount may be selected based on predetermined criteria. In otherinstances, a default payment account may not have been established forthe circumstances associated with a transaction.

FIG. 6 illustrates one implementation of user interface 22 conveying adefault payment account 44 to the user and enabling the user to acceptor reject the default payment account via an accept option 46 or areject option 48. Other implementations of user interface 22 enablingthe user to accept or reject the default payment account arecontemplated in which more or less information may be provided to theuser. For example, FIG. 7 illustrates an implementation of userinterface 22 that conveys the default payment account along with theamount for the transaction. In the implementation of FIG. 7, the user isenabled to reject the amount for the transaction in addition to, orinstead of, the payment account.

In the event that the user rejects the default payment account, or inthe absence of a default payment account, user interface 22 may presentthe user with a plurality of payment methods. FIG. 8 illustrates userinterface 22 providing the user with a plurality of payment methodoptions 50. The possible payment methods may comprise differentcategories of payment accounts stored by account module 32. Forinstance, the payment methods may comprise a credit payment method, adebit payment method, a prepaid payment method, a gift payment method,and/or other payment methods. The presentation of payment method options50 to the user may convey a ranking of the payment methods associatedwith payment method options 50. The payment methods may be ranked fromthe most likely to be selected by the user to the least likely to beselected by the user. This may be determined based on one or morepredetermined criteria, such as past payment method usage gleaned fromstored transaction records and/or other user settings. It should beappreciated that in some implementations, user interface 22 may skip thepresentation of payment methods, and may instead simply provide aplurality of possible payment accounts. In some of theseimplementations, the payment accounts provided to the user may includepayment accounts associated with a default payment method.

As is illustrated in FIG. 9, upon selection of a payment method for thetransaction, user interface 22 may present a plurality of defaultsetting options 52 that may enable the user to set the selected paymentmethod as a default payment method for future transactions. Defaultsetting options 52 may enable the user to set the selected paymentmethod as the default payment method for transactions at a currentlocation, at a current retailer, for transactions above a pricethreshold, for transactions below a price threshold, at retailers of acurrent retailer type, during a specified time period (e.g., a timeperiod each day, a time period each week, a time period each month, atime period each year, until a specified time, etc.), a combination ofconsiderations, for all transactions, for no future transactions, and/orbased on other considerations.

As can be seen in FIG. 10, upon selection of a payment method, userinterface 22 may present to the user a plurality of payment accountoptions 56 enabling the user to select a payment account for thewireless point-of-sale transaction. The presentation of payment accountoptions 56 to the user may convey a ranking of the payment accountsassociated with payment account options 56. The payment accounts may beranked from the most likely to be selected by the user to the leastlikely to be selected by the user. This may be determined based on oneor more predetermined criteria, such as past payment method usagegleaned from stored transaction records and/or other user settings. Itshould be appreciated that payment account options 56, as shown in FIG.10, may be presented to the user immediately (or substantially so) uponinitiation of the wireless point-of-sale transaction without enabling(or requiring) the user to manually select a payment method, with thehighest ranked payment account constituting the default payment account.

As is illustrated in FIG. 11, upon selection of a payment account forthe transaction, user interface 22 may present a plurality of defaultsetting options 58 that may enable the user to set the selected paymentaccount as a default payment account for future transactions. Defaultsetting options 58 may enable the user to set the selected paymentaccount as the default payment account for transactions at a currentlocation, at a current retailer, for transactions above a pricethreshold, for transactions below a price threshold, at retailers of acurrent retailer type, for transactions made when the balance of thepayment account is above a balance threshold, for transactions made whenthe balance of the payment account is below a balance threshold, duringa specified time period (e.g., a time period each day, a time periodeach week, a time period each month, a time period each year, until aspecified time, etc.), a combination of considerations, for alltransactions, for no future transactions, and/or based on otherconsiderations.

It should be appreciated that default setting options 52 and/or 58 maybe accessed and/or adjusted at a time when a wireless point-of-saletransaction is not being conducted. For example, some or all of defaultsetting options 52 and/or 58 may be accessed and/or adjusted byselecting a default action option from a menu of action options similarto the one illustrated in FIG. 5. In some implementations, when adefault payment account is frequently rejected by the user in favor of amanually selected account for a series of transactions that have certaincriteria in common, processor 20 may cause a suggestion to be made tothe user via user interface 22 that the manually selected account beimplemented as the default payment account for the criteria shared bythe series of transactions. This may enhance the efficiency associatedwith the use of a default payment account.

As was mentioned above with respect to FIGS. 1 and 2, once a paymentaccount has been selected by the user for the wireless point-of-saletransaction, payment information may be wirelessly transmitted bywireless client device 12 that enables point-of-sale device 14 to securepayment (or promise of payment) for the transaction. In response to thepayment (or promise of payment), point-of-sale device 14 may generateone or more transaction records that may be provided to wireless clientdevice 12. In some instances, the transaction records may include anelectronic transaction record. For instance, an electronic transactionrecord may be transmitted to wireless client device 12 frompoint-of-sale device 14, financial institutions 16, alternate client 18,transaction server 40 (FIGS. 3 and 4), or otherwise transmitted towireless client device 12. In some of these instances, the electronictransaction record may be wirelessly transmitted to wireless clientdevice 12 at the conclusion of the transaction, or relatively soonthereafter. The electronic transaction record may include transactioninformation such as a transaction amount, a transaction date, atransaction time, a transacting party (e.g., a retailer, etc.), a type(or classification) of transacting party (e.g., a type of retailer,etc.), an itemized list of goods and/or services purchased (orreturned), classifications of one or more goods and/or servicespurchased, a location, and/or other transaction information.

In some implementations, wireless client device 12 may generate anelectronic transaction record. The generated transaction record mayinclude transaction information available to wireless client device 12without receiving information from point-of-sale device 14 (directly orindirectly). For example, the generated transaction record may include atransaction date and/or time (e.g., as indicated by a clock and/orcalendar associated with wireless client device 12), a transactionamount, a location (e.g., as indicated by a global positioning systemcapability, or other position indicating capability provided by wirelessclient device), and/or other transaction information. In some instances,user interface 22 may enable the user to input additional transactioninformation to add more transaction information to the electronictransaction record. For instance, the user may input a transactingparty, a type of transacting party, one or more classifications of oneor more goods and/or services purchased, and/or other transactioninformation. Some transaction information included in the electronictransaction record generated by wireless client device 12 may beinferred based on known transaction information. As a non-limitingexample, a physical location of the transaction may enable an inferenceof a retailer associated with point-of-sale device 14.

FIG. 12 illustrates an example of a transaction record displayed on userinterface 22 to the user. The user may be enabled via user interface 22to accept or reject the transaction record for storage. Upon storage ofthe transaction record, account module 32, user spending module 36,and/or alert module 38 may implement the information included in thetransaction record in the manner discussed above. In some instances, thetransaction record may not be displayed at the end of the transactionunless requested by the user.

In one or more implementations of the invention, once the transactionrecord has been received and/or generated by wireless client device 12,a classification, or type, may be assigned to items purchased in thetransaction, or to the transaction as a whole. FIG. 13 illustrates animplementation in which user interface 22 may convey a defaultclassification 60 assigned to the transaction as a whole. In someinstances, the default classification 60 may be included in thetransaction record transmitted to wireless client device 12. In otherinstances in which the transaction record is generated by wirelessclient device 12 or in which the transaction record transmitted towireless client device 12 does not include a default classification. Thedefault classification may be determined based on one or morepre-determined criteria.

As can be seen in FIG. 13, the user may be enabled to accept the defaultclassification, reject the default classification, or tag theclassification for later review. In some implementations, the defaultclassification may be displayed to the user relatively quickly after thewireless point-of-sale transaction is executed so that the user mayclassify the transaction (and/or items purchased in the transaction)while the transaction is fresh in the user's mind. However, ifcomprehensive review of the classification is not convenient for theuser, the user may tag or mark the classification for later, moreconvenient, review. The classification of the transaction (and/or itemspurchased in the transaction) may be implemented by processor 20 inbudgeting functions, threshold monitoring functions, and/or otherfunctions.

FIG. 14 illustrates an implementation of user interface 22 enabling theuser to select a classification option 62 for the transaction. In someinstances, user interface 22 may enable the user to selectclassification options 62 after the user rejects the defaultclassification. In other instances, no default classification may bedetermined, and user interface 22 may enable the user to selectclassification options 62 without providing the user with a defaultclassification. Classification options 62 may comprise a foodclassification option, a clothing classification option, anentertainment classification option, a travel classification option, awork expense classification option, and/or other classification options.One or more of classification options 62 may be automatically providedby processor 20. One or more of classification options may be manuallyentered by the user.

As is illustrated in FIG. 15, upon selection of a classification for thetransaction, user interface 22 may present a plurality of defaultsetting options 64 that may enable the user to set the selectedclassification as a default classification for future transactions.Default setting options 64 may enable the user to set the selectedclassification as the default classification for transactions at acurrent location, at a current retailer, and/or based on otherconsiderations.

FIG. 16 illustrates user interface 22 in an implementation in which theelectronic transaction comprises an itemized list of goods and/orservices purchased in the wireless point-of-sale transaction, and one ormore of the items are individually assigned a default classification. Ascan be seen, user interface 22 enables the user to accept one or more ofthe individual default classifications, reject one or more of thedefault classifications, or mark one or more of the defaultclassifications for later review.

As shown in FIG. 17, if the user rejects one or more of the individualdefault classifications, user interface 22 may present one or moreclassification options 66 to the user so that the user may manuallyclassify one or more of the individual items. In some implementations,individual default classifications may not be provided. In theseinstances the user may manually classify one or more individual itemsvia user interface 22 (e.g., using a display similar to the one shown inFIG. 17).

As was discussed previously with respect to FIG. 5, user interface 22may enable the user to view the spending history. FIG. 18 illustrates animplementation in which user interface 22 displays a plurality ofspending history viewing options 68 to the user. Viewing options 68 mayenable the user to view the spending history by time period, byclassification, by payment method, by payment account, by location, byretailer, or based on some other considerations. In someimplementations, the spending history may automatically be provided tothe user according to a default viewing option. The default viewingoption may be a user selectable setting.

Based on a selection of one of viewing options 68 (or the setting of thedefault viewing option), user interface 22 may convey the spendinghistory to the user. For example, FIG. 20 illustrates user interface 22conveying the spending history to the user in accordance with aclassification viewing option. This may include providing predeterminedtransaction information for transactions that have been classifiedwithin a selected classification or group of classifications. Forinstance, in the implementation shown in FIG. 20 the transactioninformation may comprise a transaction date, a transaction amount, apayment account, and/or other transaction information. Additionally,information related to the transactions associated with the selectedclassification (or classifications) as a whole may be conveyed to theuser by user interface 22. For example, a total amount spent ontransactions and/or items classified within the selected classificationor group of classifications may be provided. The total amount mayinclude the total amount spent on transaction and/or items within theselected classification or group of classifications in a predeterminedtime frame (e.g., over the previous 30-days, since the first of themonth, etc.). The information related to the transaction may furtherinclude other information, such as for example, a ranking of paymentaccounts according to most frequently utilized, a percentage of totaluser spending that the spending within the selected classification(s)makes up, other relative spending comparisons between classifications,and/or other information.

User interface 22 may enable the user to select a transaction to viewthe transaction record associated with that transaction. For example,upon selection of one of the transactions included in FIG. 20 thetransaction record associated with the selected transaction may bedisplayed to the user via user interface 22. FIG. 21 illustrates userinterface 22 displaying a transaction record to the user. As is shown inFIG. 21, one or more transaction record options 70 may be provided tothe user to enable the user to take an action with respect to thetransaction record. For example, the user may modify the currentclassification of the transaction and/or individual classifications ofone or more items included in the transaction. As another example, theuser may cause the transaction record to be transmitted. This mayinclude wireless transmission of the transaction record to point-of-saledevice 14 as proof of purchase (e.g., a receipt) during an “exchange” or“return” transaction.

Referring back to FIG. 18, further examples of user interface 22presenting the spending history to the user in accordance with otherones of viewing options 68 are not explicitly depicted. However, itshould be appreciated that the presentation of the spending history inaccordance with the omitted ones of viewing options 68 may followsubstantially from the depiction in the drawings and the descriptionabove of the presentation of the spending history with respect to timeperiod and classification. Further, it should be understood that thedepictions of the presentations made are not limiting, and that otherschemes for presenting the spending history may be implemented. Forexample, combinations of viewing option may be made to convey thespending history to the user. As another example, pie charts, graphs,and/or other visual means may be used to display the spending history tothe user without departing from the scope of the present invention. Insome implementations, the spending history may be displayed to the userin conjunction with one or more spending thresholds to enable the userto monitor current spending levels with predetermined, or budgeted,spending levels.

As was discussed above with respect to FIG. 5, user interface 22 mayenable the user to select an action option associated with settingthresholds. In one implementation, setting thresholds may comprisesetting spending thresholds. Spending thresholds may be associated witha predetermined future spending level, rate, and/or amount associatedwith a budget, and the spending thresholds may be used as a tool by theuser to adhere to the budget. FIG. 22 illustrates user interface 22providing the user with threshold basis options 72. Threshold basisoptions 72 may comprise setting a spending threshold on a pertransaction basis, on a per time period basis (e.g., over a rolling timeperiod, between predetermined time demarcations, etc.), and/or on otherbasis. Once a basis for the threshold has been established, the user mayinput a threshold amount. This amount may constitute the monetary amountof spending over the selected basis that will “breach” the spendingthreshold.

As is illustrated in FIG. 23, upon selection of a per transaction or aper time period basis, user interface 22 may enable the user to selectone or more threshold options 74 which may be used to determine whichtransactions and/or purchased items should be applied toward thespending threshold. For example, threshold options 74 may comprise aclassification option, a payment method type option, a payment accountoption, a location option, a retailer option, a combination of options,and/or other options. Once the user has selected the appropriate optionsfor the threshold, transactions and/or purchased items associated withthe selected ones of threshold options 74 will be applied toward thethreshold.

As has been addressed above, when a spending threshold is breached analert may be generated. FIG. 24 illustrates a plurality of alert options76 presented to the user by user interface 22. When the spendingthreshold is breached, the generated alert(s) may be generated inaccordance with the alert options 76 presented to the user. Alertoptions 76 may comprise a visual alert option, an audible alert option,a third party alert option, a restrict payment option (e.g., “freezing”one or more payment accounts, etc.), and/or other options.

Returning to FIG. 5, the selection of a search transaction recordsaction option may enable the user to search for a particular transactionrecord or group of transaction records. It should be appreciated thatthe functionality described above with respect to the viewing of thespending history via user interface 22 enables the user to search forspecific transaction records by viewing lists of transaction organizedby time period, classification, payment method, payment account,location, retailer, and/or other considerations, and accessingindividual transaction records for the transactions so organized.However, other searching functionality is contemplated, including textsearching, searching by date, and/or other searching capabilities. Theselection of the search transaction records action option may enable theuser to access these additional searching functions and/or capabilities.

It should be understood to one of ordinary skill in the art that thedepiction of user interface 22 in FIGS. 5-24 and the accompanyingdescription found herein are provided for the purpose of explaining thefunctionality of user interface 22, and that other implementations ofuser interface 22 providing some or all of the functionality describedabove, as well as additional functionality in some instances, fallwithin the scope of the invention.

Throughout the description above the term user has been usedinterchangeably to describe both single individuals and groups ofindividuals acting in concert.

Thus, the invention has been fully and completely described. However, itshould be appreciated that the description provided above is in no wayintended to be limiting. Instead, the invention should only be limitedby the scope of the claims provided hereafter.

1. A system that enables a wireless point-of-sale transaction, thesystem comprising: an account module that stores account informationcorresponding to a plurality of payment accounts; an account selectionmodule that selects a payment account from the plurality of paymentaccounts as a default payment account for a wireless point-of-saletransaction based on one or more predetermined criteria; a display thatdisplays the default payment account to a user; an input interface thatenables the user to accept the default payment account by the accountselection module; and a wireless transmitter that wirelessly transmitspayment information to a point-of-sale device, wherein the paymentinformation comprises account information associated with the defaultaccount when the default payment account is accepted via the inputinterface.
 2. The system of claim 1, wherein the one or morepredetermined criteria comprise one or more of a retailer, a physicallocation, an account balance, a type of a good and/or service beingpurchased, a transaction amount, or a time.
 3. The system of claim 1,wherein the one or more predetermined criteria comprise at least onecriterion determined based on a user preference.
 4. The system of claim1, wherein the input interface enables the user to reject the defaultpayment account selected by the account selection module and manuallyselect a user-preferred payment account from the plurality of accountsstored in the account module, and wherein the payment informationcomprises account information associated with the user-preferred paymentaccount when the user-preferred payment account is manually selectedfrom the plurality of accounts stored in the account module.
 5. Thesystem of claim 1, wherein the one or more predetermined criteriacomprise user spending information that includes one or more aspects ofone or more transaction records of one or more previous wirelesspoint-of-sale transactions.
 6. A system that enables a wirelesspoint-of-sale transaction, the system comprising: an account module thatstores account information corresponding to a plurality of paymentaccounts; a display that displays two or more of the payment accountsstored by the account module to a user; an input interface that enablesthe user to select one of the payment accounts displayed by the display;and a wireless transmitter that wirelessly transmits payment informationto a point-of-sale device, wherein the payment information comprisesaccount information associated with the selected payment account.
 7. Thesystem of claim 6, further comprising an account selection module thatranks the payment accounts displayed by the display based on one or morepredetermined criteria, and wherein the payment accounts are displayedby the display in a manner that reflects the ranks of the paymentaccounts.
 8. The system of claim 7, wherein the one or morepredetermined criteria comprise one or more of a retailer, a physicallocation, an account balance, a type of a good and/or service beingpurchased, a transaction amount, or a time.
 9. The system of claim 7,wherein the one or more predetermined criteria comprise at least onecriterion determined based on a user preference.
 10. The system of claim7, wherein the one or more predetermined criteria comprise a transactionrecord that includes one or more aspects of one or more previouspoint-of-sale transactions.
 11. A system that enables a wirelesspoint-of-sale transaction, the system comprising: an account module thatstores account information corresponding to a payment account, whereinthe account information comprises balance information related to thepayment account; an input interface that enables a user to initiate awireless point-of-sale transactions; a transmitter that wirelesslytransmits payment information to a point-of-sale device in response tothe initiation of the wireless point-of-sale transactions, wherein thepayment information comprises account information associated with thepayment account stored by the account module; and a receiver thatreceives a wireless transmission of purchase information, wherein thepurchase information comprises price information related to the wirelesspoint-of-sale transaction; wherein the balance information stored by theaccount module is updated based on the price information related to thewireless point-of-sale transactions.
 12. The system of claim 11, whereinthe price information received by the receiver is an itemized price listof goods and/or services acquired by the user in the wirelesspoint-of-sale transaction.
 13. The system of claim 12, wherein the priceinformation is stored and the system enables a second wirelesspoint-of-sale transaction in which the user receives a refund for someor all of the goods and/or services purchased in the first wirelesstransaction, wherein the input interface enables the user to select thetransaction information associated with the goods and/or services andthe transmitter wirelessly transmits the selected transactioninformation to a point-of-sale device.
 14. The system of claim 11,further comprising a user spending module that tracks the user'sspending based on the received transaction information.
 15. The systemof claim 14, wherein the input interface enables the user to input oneor more spending thresholds that are stored by the user spending module,and wherein the user spending module compares the user's spending withthe one or more spending thresholds.
 16. The system of claim 15, furthercomprising an alert module, wherein when the user's spending exceeds oneor more of the spending thresholds the alert module generates an alert.17. The system of claim 16, wherein the alert generated by the alertmodule is provided to the user.
 18. The system of claim 16, wherein thealert generated by the alert module is provided to a third-party. 19.The system of claim 12, further comprising a user spending module thattracks the user's spending with a respect to a plurality ofclassifications of goods and/or services based on the receivedtransaction information.
 20. The system of claim 19, wherein the inputinterface enables the user to individually assign a classification ofgood and/or service to the goods and/or services acquired by the user inthe wireless point-of-sale transaction.
 21. The system of claim 19,wherein the goods and/or services acquired by the user in the wirelesspoint-of-sale transaction are automatically assigned to classificationsof goods and/or services.